FrontPage 98 Server Extensions Patches and Version Numbers

Checking Version Numbers

To determine the version number of the FrontPage Server Extensions on a particular web server, open the web with the Windows Explorer and click the Tools Web Settings command.   On the Configuration tab, there is a FrontPage Server Extensions Version field.

On Windows server, the version number can also be obtained from the FrontPage Server Administrator application.

On UNIX servers the version number can be obtained by running /usr/local/frontpage/currentversion/exes/_vti_bin/shtml.exe -version.

UNIX Server Extensions Versions

Release Date Version Number Description
Initial FrontPage 98 product release 3.0.2.0913 Initial release to http://www.microsoft.com/frontpage website and included on the retail FrontPage 98 CD-ROM.
10/21/97 3.0.2.0913 Released to http://www.microsoft.com/frontpage website.

Fixes security issues with the FrontPage Apache patch.  No changes to the core Server Extensions themselves, thus the version number of the server extensions did not change.  No change or update required for any server other than Apache with the FrontPage patch installed.

The version string reported by Apache indicates whether the fixed FrontPage Apache patch is installed:

  • Apache/1.2.4 FrontPage/3.0.2  The fix is not installed.
  • Apache/1.2.4 FrontPage/3.0.3  If the FrontPage number is 3.0.3 or higher then the fix is installed.
12/12/97 3.0.2.1117 Released to http://www.microsoft.com/frontpage website.

For Apache web servers, do not require write access to httpd.conf in order to run the FrontPage Server Extensions.  Write access to httpd.conf is required in order to install the FrontPage Server Extensions, but not to run the extensions for remote authoring and publishing.

Windows Server Extensions Versions

Release Date Version Number Description
Initial FrontPage 98 product release 3.0.2.0926 Initial release to http://www.microsoft.com/frontpage website and included on the retail FrontPage 98 CD-ROM.

Although this release installs on IIS 4.0, do not use the 3.0.2.0926 Server Extensions with IIS 4.0 because bug fixes were made in the period after the FrontPage 98 release date and before the IIS 4.0 release date.  Use the version 3.0.2.1105 or later Server Extensions that are included in the IIS 4.0 setup.

IIS 4.0 initial product release 3.0.2.1105 Server Extensions update for IIS 4.0.  This version of the Server Extensions is included in the IIS 4.0 setup package and is not on the FrontPage 98 retail CD.  This version also does not support any server type other than IIS 4.0.

To install use the FrontPage Server Extensions option in the IIS 4.0 Custom setup.

12/15/97 3.0.2.1313 Released to http://www.microsoft.com/frontpage website.

On IIS 4.0, the version 3.0.2.1313 Server Extensions are changed to create individual application roots by default for each FrontPage web or subweb. These application roots are used to mark the FrontPage Extension DLLs as in-process applications.  Before this change the IIS 4.0 global setting InProcessISAPIApps was used to run the FrontPage Extension DLLs in-process, which is a small security risk if users are allowed to upload and execute their own ISAPI DLLs.

Fix multihosted server support for O'Reilly WebSite web servers.  Single hosted server support worked before version 3.0.2.1313, but multihosted sites did not.

2/10/98 3.0.2.1330 Released to http://www.microsoft.com/frontpage website, and included in the A release of the FrontPage 98 CD-ROM.

Fixes a security issue that allows the source code of interpreted scripts such as Active Server Pages (ASP) to be viewed by a browser of the website, without requiring authoring permissions to the website.  The fix prevents the FrontPage executable shtml.dll (or shtml.exe) from echoing pages that do not contain a runtime FrontPage Component such as a Search Component or a Discussion Component.